<?php
/**
 * <https://y.st./>
 * Copyright © 2015 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'<{title}>' => 'The Republic of Cabo Verde',
	'<{body}>' => <<<END
<p>
	The Republic of Cabo Verde&apos;s registry got back to me today, sending the user name needed to log in with.
	It seems the system works, there&apos;s just a bit of a delay.
</p>
<p>
	Seeking more words to feed into eschalot, I took a look at <a href="file:///usr/share/dict/"><code>/usr/share/dict/</code></a> on my system.
	There are four files there.
	<code>american-english</code> is a huge word list.
	The first is a document explaining how to set your default word list.
	The other three are supposed to be word lists, but <code>american-english</code> is the only actual word list.
	<code>words.pre-dictionaries-common</code> is just a symbolic link to <code>american-english</code> and <code>words</code> is a symbolic link to <code>/etc/dictionaries-common/words</code>, which in turn is a symbolic link back to <code>american-english</code>.
	Having only one word list available, I opened the <code>american-english</code> file only to find that many of the words use non-English accents, such as the word &quot;Ångström&quot;.
	These words would not do well in eschalot, so I had grep sort out everything that was not usable, and fed the remaining list to eschalot.
</p>
<p>
	I noticed a couple things with eschalot&apos;s handling of word lists.
	First, eschalot does not understand any word shorter than eight characters.
	I confirmed this by attempting to use the <code>-l</code> flag to specify that shorter words be used; any lower bound that is shorter than eight characters halts the program, showing the usage instructions.
	Second, eschalot stops after finding a single word in the list; it does not attempt to create a better onion by stringing multiple random words together.
	I first tried to fix this by using the included worgen utility to find every combination of words available, but that quickly started filling up my hard drive and I had to abandon that plan.
	Next, I built a script that lower cased every word on the list, then built a regular expression of of them.
	I figured if I could compact the words into a single expression, I could just run &quot;eschalot -r &apos;^({expression})+\$&apos;&quot;, but that didn&apos;t work out either.
	Eschalot complained that the argument list was too long.
	I tried hacking away at the world list, removing short words and such, but I got to the point where I was removing way too much long before I hit something eschalot could process.
</p>
<p>
	While I was still on the first stage of onion finding, searching using the word list that had the words containing Unicode characters striped out, I ended up with a fairly-usable onion: <code>//unseatedaltleuhs.onion</code>.
	I don&apos;t know what an &quot;altleuh&quot; is, but it&apos;s pronounceable, and amusing this bogus word is a noun, it makes sense that some of them might be unseated.
	I briefly considered using it as a surname instead of &quot;Dawson&quot;, but quickly rejected that idea.
</p>
<p>
	ICANN and eNom have been hassling <a href="https://wowana.me">wowaname</a> about her use of an invalid mailing address in her whois record for a name she has registered under a $a[gTLD].
	They want her to add a verifiable postal address, so I offered her the use of mine so she wouldn&apos;t have to divulge her own location.
	After all, I&apos;m already in the whois database, I&apos;ve got nothing to hide.
	SHe took me up on my offer, so I am now authorized to receive mail on Opal Hart&apos;s behalf.
	According to ICANN rules, that makes my address valid for use in her whois records.
	Her email address, which was only invalid accidentally, has also been corrected, so all that leaves it the incorrect telephone number.
	I&apos;m hoping that they do not hassle her about that as well.
</p>
<p>
	My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
</p>
END
);
